Add keep_ram_copy_of_weights
config option
#7565
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a
keep_ram_copy_of_weights
config option. The default (and legacy) behavior istrue
. The tradeoffs for this setting are as follows:keep_ram_copy_of_weights: true
: Faster model switching and LoRA patching.keep_ram_copy_of_weights: false
: Lower average RAM load (may not help significantly with peak RAM).Related Issues / Discussions
QA Instructions
Test with
enable_partial_load: false
andkeep_ram_copy_of_weights: false
.Test with
enable_partial_load: false
andkeep_ram_copy_of_weights: true
.Test with
enable_partial_load: true
andkeep_ram_copy_of_weights: false
.Test with
enable_partial_load: true
andkeep_ram_copy_of_weights: true
.Smoke test CPU-only and MPS with default configs.
Merge Plan
Checklist
What's New
copy (if doing a release after this PR)